Skip to content

Conversation

@gustavo-grieco
Copy link
Contributor

No description provided.

@gustavo-grieco gustavo-grieco changed the title Added L2 to L1 message failure as a possible issue Added L1 to L2 message failure as a possible issue Sep 23, 2022
@montyly montyly requested a review from smonicas September 28, 2022 08:55
@montyly
Copy link
Contributor

montyly commented Sep 28, 2022

@smonicas can you take a look at it?


If a L1 message is never processed by the sequencer, users will never receive their tokens either in L1 or L2, so they need to way to cancel it.

As a more real example, a recent [AAVE audit](https://github.com/aave-starknet-project/aave-starknet-bridge/pull/106#issue-1336925381) highlighed this issue and required to add code to cancel messages.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be moved to a Examples section at the bottom I think

montyly and others added 2 commits October 28, 2022 14:34
Co-authored-by: Simone <79767264+smonicas@users.noreply.github.com>
Co-authored-by: Simone <79767264+smonicas@users.noreply.github.com>
@montyly montyly merged commit 3e846a1 into master Nov 3, 2022
@montyly montyly deleted the dev-consider-L2-L1-message-can-fail branch November 3, 2022 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants